Option to persist mails in sqlite database at path - #109

The idea was to make it transparent, so no options should be involved really. My delay on this feature was just researching a nice way to find a platform-dependent location for the database.

Any chance to have this PR merged ? Why not providing a default sqlite storage path so that it remain transparent by default and allowing this parameter to override it ?

I need to launch several mailcatcher instances on the same server, so I really need to be able to have several sqlite persistance path.

I would prefer a --database=URL argument, using something like sequel, falling back to ENV.fetch("DATABASE_URL", "sqlite://:memory:"), and with graceful migrations. This would work but would create a new migration path for which I'm not keen.

@fdrouet you can already run multiple instances of mailcatcher using different ports, the content just won't survive restarts. :-)

@sj26 yes you are right but it is not sufficient in my case as I would like to use mailcatcher on an acceptance testing platform with lots of email sent and I would like to avoid consuming all the server memory with mailcatcher processes

@fdrouet you might like to try https://github.com/mailhog/mailhog. It's written in go, has less dependencies and much less memory usage.

Thanks for the hint